home *** CD-ROM | disk | FTP | other *** search
/ ftp.cs.arizona.edu / ftp.cs.arizona.edu.tar / ftp.cs.arizona.edu / icon / newsgrp / group93b.txt / 000131_icon-group-sender _Thu Jun 10 04:38:21 1993.msg < prev    next >
Internet Message Format  |  1993-06-16  |  1KB
  1. Received: from owl.CS.Arizona.EDU by cheltenham.CS.Arizona.EDU; Fri, 11 Jun 1993 09:04:21 MST
  2. Received: by owl.cs.arizona.edu; Fri, 11 Jun 1993 09:04:20 MST
  3. Date: 10 Jun 93 04:38:21 GMT
  4. From: swrinde!cs.utexas.edu!uwm.edu!linac!uchinews!ellis!goer@gatech.edu  (Richard L. Goerwitz)
  5. Organization: University of Chicago
  6. Subject: Re: Initialization files for Icon programs
  7. Message-Id: <1993Jun10.043821.198@midway.uchicago.edu>
  8. References: <677397@MTS.cc.Wayne.edu>
  9. Sender: icon-group-request@cs.arizona.edu
  10. To: icon-group@cs.arizona.edu
  11. Status: R
  12. Errors-To: icon-group-errors@cs.arizona.edu
  13.  
  14. In article <677397@MTS.cc.Wayne.edu> Paul_Abrahams@MTS.cc.Wayne.edu writes:
  15. > 
  16. >So here's the problem: how, within the program, can I determine the full
  17. >path name of the icode file so that I can construct the full path name of
  18. >the initialization files?
  19.  
  20. Paul, I wonder why you'd want to do this, at least under UNIX.  UNIX
  21. executables usually go in a bin directory.  Initialization files go in
  22. a lib directory.  They get hashed separately, and their permissions
  23. and ownership conventions differ.
  24.  
  25. -- 
  26.  
  27.    -Richard L. Goerwitz              goer%midway@uchicago.bitnet
  28.    goer@midway.uchicago.edu          rutgers!oddjob!ellis!goer
  29.